I’m designing for the web. The infinitely flexible web. The web that doesn’t have one screen size, one browser, one operating system, or one device. The web that can be used by anyone, anywhere, on any internet connection, on any device, on any operating system, on any browser, with any screen size. I’m designing with the web. Using the web platform. I have a deep understanding of HTML and its semantics. I love CSS, I know how and when to utilise its many features, and I keep up-to-date as more are added. I have a strong understanding of modern JavaScript and most importantly I know when not to use it.
Also an accessibility specialist. My expertise goes beyond what web designers need to know. I’m also a design system specialist. I’m a systems thinker. I love standardizing things to simplify the web development process. [...] I love human-centred design and co-design—nothing about us without us.
A collection of resources such as guides, blog posts, advocacy, how to's
Nice resources about accessibility on the web
- Utiliser le camelcase
- Positionner ces hashtags à la fin de la publication pour éviter d’alourdir leur restitution par les lecteurs d’écran.
- Utiliser les accents afin que ces mots soient correctement lues
Les exemples données sont aussi en fichiers audio.
See the diff of two crate versions directly in the browser. All is happening in the browser 😳
And now, imagine that this place is your personal website, under your own domain name, under your control.
This is the basic idea behind the IndieWeb.
Most tools and ideas of the IndieWeb is Publish Own Site, Syndicate Elsewhere.
Another is Webmentions.
Good job!
Similar to Days since last Facebook scandal, but for Web 3.
Another blogging platform
Create a web design based on Code Lyoko graphics
It seems that many of the products Google actively encourage web authors to add to their sites are paradoxically the ones that have the worst impact on performance.
The amount of data they collect goes far beyond what is useful to the end user, and is undoubtedly a contributor to the huge proportion of “junk data” stored in datacentres worldwide.
I recently made the case for this at work while making improvements to the company website, and my manager admitted that they rarely look at the analytics.
It seems to be a cool web project to extend HTML to the backend.
- Interop project https://github.com/web-platform-tests/interop
- Open Web Docs through contributions to MDN https://openwebdocs.org/
- WebFC Community group https://www.w3.org/community/webdx/
Still competitions on the web, but without fragmentation.
We want to make it easier for developers to track the list of features that are widely available and those that are under development.
To contribute:
- WebDX Community Group
- Ideas on github repositories
Exactly the project I wanted to build: display URL informations and their names.
How to link webmentions.io messages, likeCount, replyCount and reportCount to a personal blog with a few JS lines.
Crazy how much MB of JS are needed
- It's bloated with useless stuff for the users
AMP’s biggest advantage is the restrictions it draws on how much stuff you can cram into a single page.
As bullshit jobs exist, so do bullshit webpages
The authors think the url does not really matter anymore because
- they are not fully displayed in some browsers
- they need to be short and memorable to get people to it
So it does not need to contain a lot of information.